init/FreeBSD: fix xencommons so it can only be launched by Dom0
authorRoger Pau Monne <roger.pau@citrix.com>
Mon, 19 Dec 2016 15:02:03 +0000 (15:02 +0000)
committerIan Jackson <Ian.Jackson@eu.citrix.com>
Wed, 4 Jan 2017 17:06:36 +0000 (17:06 +0000)
commit3667bc0394743085548c85632b8dc5c3d77483d7
tree2f4ad7dd2e2bed832e7165a7c107d8db080a207c
parent86e54bea2bbaa01cbb4b04ec73dee459b89734f2
init/FreeBSD: fix xencommons so it can only be launched by Dom0

At the moment the execution of xencommons is gated on the presence of the
privcmd device, but that's not correct, since privcmd is available to all Xen
domains (privileged or unprivileged). Instead of using privcmd use the
xenstored device, which will only be available to the domain that's in charge
of running xenstored, and thus xencommons.

Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
(cherry picked from commit c875b9778da0c56a0c118626771465b87df31fe8)
tools/hotplug/FreeBSD/rc.d/xencommons.in